The 640 MEG Shareware Studio 2

home *** CD-ROM | disk | FTP | other *** search

/ The 640 MEG Shareware Studio 2 / The 640 Meg Shareware Studio CD-ROM Volume II (Data Express)(1993).ISO / prog / pdt_set2.zip / PDT-SET2.DOC < prev next >

Wrap

Text File | 1992-03-11 | 101KB | 2,148 lines

███████┐▐████████┐ ████████┐ ██┌──██│ └██┌──██│ └──██┌──┘ ███████│ ██│ ██│ ██│ ██┌────┘ ██│ ██│ ██│ ██│ ▐████████│ ██│ └─┘ └───────┘ └─┘ ████████┐ ███████┐ ███████┐ ██┐ ██┐ ███┐ ████┐ ████████┐ └──██┌──┘ ██┌──██│ ██┌──██│ ██│ ██│ ██┌┘ └██┌┘ └──██┌──┘ ██│ ██│ ██│ ██│ ██│ ██│ ███████┐ ██│ ██│ ██│ ██│ ██│ ██│ ██│ ██│ ██┌──██│ ██│ ██│ ██│ ███████│ ███████│ ██████┐ ██│ ██│ ████┐ ██│ └─┘ └──────┘ └──────┘ └─────┘ └─┘ └─┘ └───┘ └─┘ Set #2 Version 1.4 (3/29) ┌────────────────────────── Set #2 ───────────────────────────┐ │ │▄ │ Set #2 includes FIELDS.Exe, DBF-ASC.Exe and ASC-DBF.Exe │█ │ to convert dBase files to "comma-delimited ASCII files," or│█ │ comma-delimited ASCII files to dBase files, respectively. │█ │ │█ │ As we'll explain later, PDT's Tool Kit contains many things│█ │ to help you create, convert and manage data files. Some │█ │ programs are offered in "shareware versions" as "sets." │█ └─────────────────────────────────────────────────────────────┘█ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Overview ──────── The PDT Tool Kit includes several things to help you manage, edit, convert and repair data files -- dBase files, or fixed- length files created by other programs. Uses include: * Quickly create dBase files with any field structure. Help you create "dictionaries" of field names to serve as a per- manent reminder of what fields in dBase files are for. * Create "sub-sets" of (or modify) dBase files. YOU specify which fields to include. You can delete fields, add fields, change field: lengths, types, number of decimal places, etc. * Quickly convert dBase files to comma-delimited ASCII files. Or, do the opposite: read ASCII files and save the data to dBase files. These small, fast programs simplify sharing data between different programs. * Review, understand or repair dBase files. Copyright 1992, Rob W. Smetana, All Rights Reserved 132 Alpine Terrace, San Francisco, CA 94117 (415) 863-0530 PDT, Pro~Formance Data Tool, PDT Tool Kit, P~F, and Pro~Formance are Trademarks of Rob W. Smetana. 2 ┌────────────────── Using Translate.Exe ────────────────────┐ │ │▄ │ As you can see, this manual contains lines, boxes, shad- │█ │ ing and other "high ASCII" characters. Some printers │█ │ can't print these -- they'll print either nothing, or │█ │ they'll print italic or other characters instead of lines. │█ │ │█ │ If your printer CAN'T print the lines and boxes you see │█ │ here, run Translate.Exe that we included. Run it this way: │█ │ │█ │ translate pdt-set2.doc ???? <enter> │█ │ │█ │ where "????" is either: │█ │ │█ │ - the name of a file (to send translated output to) │█ │ - or LPT1, LPT2 or LPT3 (to tell Translate to print │█ │ pdt-set2.Doc) │█ │ │█ │ Translate converts lines, boxes and shading into charac- │█ │ ters ANY printer can handle. For example: │█ │ │█ │ ┌────────┐ +--------+ │█ │ │This Box│ will become |This Box| │█ │ └────────┘ +--------+ │█ │ │█ │ If you tell Translate to print "to a file," you can then │█ │ browse or examine that file. Later, print it by typing: │█ │ │█ │ copy filename LPT1 <enter> (use LPT1, LPT2, LPT3 or PRN) │█ │ │█ │ │█ │ NOTE: Use Translate with ANY text file -- not just this │█ │ file. It comes in very handy when you receive text files │█ │ from authors who provide no way to remove or replace the │█ │ characters in files that your printer CAN'T print. │█ │ │█ └─────────────────────────────────────────────────────────────┘█ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Conventions We Use in this Manual ───────────────────────────────── "dBase" refers to dBase III, IV or later (not dBase II). "<cr>" means you should press Enter or Return. "Esc" means you should press Escape. "F2" means you should press Function Key F2. "Ctrl-A" or "Ctrl-D" means you should HOLD DOWN the Ctrl key and tap A or D. ─────────────────────────────────────────────────────────────── Contents ─────────────────────────────────────────────────────────────── SECTION I: Introduction Introduction .................................. 4 Getting Tool Kit Utilities; Shareware Versions 4 System Requirements; License ................. 5 To Register ................................... 6 Disclaimer and Limited Warranty ............... 7 Distributing This Software .................... 7 SECTION II: Using the Tool Kit's Programs ........ 8 General Syntax ................................ 9 Using FIELDS .................................. 10 Using DBF-ASC ................................. 11 Using ASC-DBF ................................. 17 Using CREATE \ These are part of Set #1. They Using DBF-DBF / are discussed in their own manual. SECTION III: Creating Definition Files ............ 24 SECTION IV: Error Message ........................ 27 SECTION V: Using the FIX-DBF Structure Files .... 29 Using FIX-DBF.HDR \ PDT's Registered users receive Using FIX-DBF.FLD / these to help them understand and repair dBase files. APPENDIX I: A Summary of our Many Programs ....... 30 APPENDIX II: Order Form ........................... 40 4 ─────────────────────────────────────────────────────────────── SECTION I: Introduction ─────────────────────────────────────────────────────────────── The PDT Tool Kit is a companion to PDT (the Pro~Formance Data Tool). PDT is a phenomenal program to view, edit and manage ANY file -- up to 2 gigabytes in size. And PDT offers special features that makes viewing and editing dBase (or other fixed- length database) files a snap! With PDT you can view and edit: data files, binary files (fonts, executable programs), EBCDIC or ASCII files -- ANY file of virtually ANY size! PDT's Tool Kit includes several things to help you manage, edit, convert and repair data files -- dBase files, or fixed- length or ASCII files created by other programs. First, the Tool Kit offers several, small, fast programs to help you Create or Modify dBase files, or Convert data files from one format (eg., dBase) to another (eg., ASCII). Second, the Tool Kit also contains files to help you fix ANY dBase file (or to simply explore the structure of dBase files). These "structure files" may be used with our PDT program to open dBase files, examine the dBase "header" or "field structure," and then, if necessary, edit things to fix corrupted dBase files. Availability; "Shareware" Versions ────────────────────────────────── The complete PDT Tool Kit is FREE to PDT's registered users. The PROGRAMS in the Tool Kit are also available separately as "user-supported" programs. "Shareware" versions work much like the registered versions. The only differences MAY be that: * Registered users receive the latest versions which usually have added features, greater capacity, etc. For example, we're adding features right now that'll let you "justify" fields -- something that can be critical with fields like phone numbers or ZIP/MAIL codes, and "nice-to-have" with other types of fields. Registered versions handle up to 250 fields, versus early versions designed to handle 25. * The entire PDT Tool Kit is sent FREE to PDT's registered users. Shareware versions are available separately -- in sets which consist of 1 or more related programs. For example, DBF-ASC and ASC-DBF let you convert files back and forth between dBase and comma-delimited ASCII formats. Users of shareware versions can register for each "set" of tools separately. Or they can register for the entire Tool Kit -- and get latest versions of everything, PLUS any new programs we've added! System Requirements 5 ─────────────────────────────────────────────────────────────── These programs run on IBM XTs, ATs, PS/2s and strict compatibles running DOS 2.1 or later. Monitor: Any Memory: About 128k Disk Drives: Hard disk recommended; floppy disks are fine Printer: Any. We don't use your printer. License ─────────────────────────────────────────────────────────────── These programs are NOT free software. They're neither "public domain" software nor "freeware." They are "user-supported" software. This software is Copyright 1987-1992, Rob W. Smetana. It is protected by both United States copyright law and inter- national treaty provisions. All Rights Reserved Worldwide. REGISTERED VERSIONS ─────────────────── Registered users must treat this software like a copyrighted book. You may use it on any number of computers/CPUs, pro- vided there is NO POSSIBILITY that it will be running on two or more computers at the same time. You may make a "backup" copy of this software for the sole purpose of guarding against the loss of this software and protecting your investment. SHAREWARE VERSIONS ────────────────── You may try out shareware (or "user-supported") versions to determine if they satisfies your needs. After using shareware versions beyond the trial period (30 days or 20-25 sessions), you MUST register to continue using it -- or stop using it. This is NOT free software. The next page explains the benefits of registering and how to register. * This is copyrighted software that's distributed through both retail and shareware channels. Shareware versions let you try it out before buying it. * If you paid a "shareware distributor" a $2-$6 fee for a disk that contained this program: - You paid them for copying the disk and sending it to you. - You did NOT pay for the software. NONE of the fees you pay shareware distributors go to the authors of shareware programs. If you use these programs, you must pay for them. To Register 6 ─────────────────────────────────────────────────────────────── When you register, we "say thanks" in many ways. * First, we send you the latest versions of these programs, which usually have new or enhanced features. For example, we're now adding several new features: options to "justify" fields (right or left), greater capacity (250 fields versus 25 fields), etc.. * Second, if you order the complete Tool Kit, we'll also include any new programs we've added since we wrote this. We'll also include the "FIX_DBF" files you can use with PDT to fix, repair, or simply examine dBase files. To Register ─────────── You may register in several different ways: 1. CALL (415) 863-0530 with your VISA or MasterCard number. This is the fastest way to register. It often cuts 2-3 weeks off the turn-around time -- since you needn't wait for your order to reach us and your check to clear the bank. 2. To register by mail: - Complete the order form at the end of this manual. - Or send your registration fee plus $4 shipping & handling ($8 shipping outside the U.S. and Canada), along with your name, address and phone number to: Pro~Formance (415) 863 - 0530 Rob W. Smetana 132 Alpine Terrace San Francisco, Ca 94117 DISCLAIMER and WARRANTY 7 ─────────────────────────────────────────────────────────────── Pro~Formance and Rob W. Smetana make no representations or warranties with respect to the contents or use of this manual and/or the Pro~Formance Data Tool (PDT) or PDT's Tool Kit. We specifically disclaim any express or implied warranties of merchantability or fitness for any particular purpose. We reserve the right to revise this manual and/or the programs described herein and to make changes to their operation inter- face or functionality, at any time, without notice and without obligation to notify any person or entity of such changes or revisions. DISTRIBUTING THIS SOFTWARE ─────────────────────────────────────────────────────────────── Shareware distributors, bulletin boards and user clubs may distribute "user-supported" (or shareware) versions of this software provided that: * Your company name, literature, etc. do not promote or include the words "freeware" or "free" software -- which terms misrepresent "user-supported" software. Expressly prohibited from distributing any software by Pro~Formance, Rob W. Smetana and/or Brandon S. Smetana are: American Freeware, California Freeware and U.S. Freeware. * Your firm or organization does not include among it's owners, employees, members or associates Ronald Chordigian or any member of his family. * You include, unmodified, all files included with this software including: PDT-Set2.Doc, DBF-ASC.Exe, ASC-DBF.Exe, and any other files mentioned in Readme.Bat or Packing.Lst. * You charge a "distribution fee" of no more than $8 (US). * You clearly state that continued use of "user-supported" software REQUIRES paying for the software. 8 ─────────────────────────────────────────────────────────────── SECTION II: Using the Tool Kit Programs ─────────────────────────────────────────────────────────────── Here's a summary of each program in PDT's Tool Kit. The number beside each program name indicates which "set" it's in. Set Program Description ─── ─────────── ─────────────────────────────────────────────── ALL Fields.Exe Reads field definitions from a dBase file and saves them to another file. Edit this 2nd file to create a handy "dictionary" or record of what's in dBase files, and what the purpose of each field is. 1 Create.Exe Create dBase database files -- with any structure you like! 1 DBF-DBF.Exe Modify the structure of existing dBase files. You may delete fields, add fields, change the width of fields, etc. Or, create new dBase files with field structures and data you prefer. 2 DBF-ASC.Exe DBF-ASC.Exe reads dBase files and creates 2 ASC-DBF.Exe comma-delimited ASCII files. ASC-DBF.Exe does the opposite: it reads comma-delimited ASCII files and saves dBase files. NOTE: DBF-ASC lets you save "definition files" allowing you to easily and quickly go back and forth between dBase and ASCII files. These also serve as useful records of the structure of hard-to-read ASCII files! General Syntax 9 ══════════════ In general, you'll run each program something like this: ProgramName file_1 file_2 file_3 <enter> In other words, at the DOS prompt, type the Program Name followed by 2 - 3 file names. File names will be files: * That you want to create. * That you want to read. * Or that contain information that defines the structure of data files. (Called "Definition Files." we'll explain these later.) NOTE: For each program, you must send it 1-3 file names. As we explain how to use each program, we'll explain what that program needs. If you can't recall how to run a program, at the DOS prompt just type: ProgramName <enter> The program will beep and display the syntax you should use to run it. ALSO NOTE: Some programs need "definition files." * These are simple ASCII files you can create with any editor or word processor. * They define the "fields" in data files: the name of each field, how wide it is, and what "type" of field it is (ie., Character, Numeric, Date, etc.) When we discuss each program, if a definition file is needed, we'll explain the format to use. See SECTION III: Definition Files used by Tool Kit Programs, for specific details on creating these files. Using Fields 10 ─────────────────────────────────────────────────────────────── Name: Fields.Exe. Purpose: * When you create a database file, you have a clear idea of what each field in the data file is for. But suppose you get promoted and someone else is assigned to manage that data file! They may have no idea what each field is for -- especially when field names are a terse 1-10 characters long as they are in dBase files. * Fields.Exe helps you create a record (dictionary) of what a database file is for, which fields are in it, and what the purpose of each field is. * Fields will read the field definitions from a dBase file and save them to another file (a ".!!!" file). YOU should then edit this 2nd file. Beside each field name, add a description of what that field is used for. NOTE: Whenever you use Create.Exe, we urge you to immedi- ately run Fields on the dBase file you just created! Syntax: fields dbase.dbf <enter> Replace "dbase.dbf" with the name of the dBase file you want to read Be sure to specify a drive/directory if your dBase file is elsewhere. If we can't find "dbase.dbf" we'll print an error message and end. If a file already exists called "dbase.!!!", we'll end, telling you to rename or delete it first. Requires: Nothing. Running Type: fields dbase.dbf <enter> Fields: Fields will quickly read the "header" of the dBase file and save the "field definitions" in a file called "dbase.!!!" -- with the same name as your dBase file, but with a ".!!!" extension. We'll save "dbase.!!!" on the same drive/directory as "dbase.dbf. Now EDIT dbase.!!! and, beside each field, enter a description of what that field is for. When you're done, print the file: copy dbase.!!! prn <enter>. That's it! Fields is small and very fast. Using DBF-ASC 11 ─────────────────────────────────────────────────────────────── Name: DBF-ASC.Exe. Purpose: * DBF-ASC reads dBase files and saves data to comma- delimited ASCII files. YOU specify which fields to save, deleting fields you don't want saved. You can also ADD fields. These fields won't be in the dBase file, but this option lets you create blank "placeholders" for fields you want to add data to later. This is especially useful when you later use ASC-DBF. These blank place- holders will turn into full-fledged dBase fields. * ALSO SEE the companion program ASC-DBF.Exe. Together, DBF-ASC and ASC-DBF let you quickly go back and forth between ASCII files (which are space-efficient, but hard to review and edit) and dBase files (which PDT lets you view and edit easily, but which are less space-efficient). * OPTIONAL DBF-ASC will also save "definition files" for you. The main purpose of these file is to let you use ASC-DBF to instantly turn your ASCII file back into a dBase file! NOTE: Database programs, word processors, spread- sheet programs, etc., often save data in their own, unique format. The comma-delimited ASCII format has evolved as an industry-standard way for programs to share data amongst themselves -- overcoming the limitations of their proprietary data formats. The ASCII format is quite disk-space-efficient. But data in this form is v-e-r-y hard to review and edit. For example, ASCII files look like this: "Title","FirstName","LastName","Address", ..... "", "Mary", "Simpson","P.O. Box 32453", ..... "Dr.", "Joseph P.", "O'Brien","17434 Oak, Suite #201" Stare at this long enough and you could go blind or insane. But notice there's no wasted space. Com- pare that with this dBase, fixed-format equivalent: TITLE FIRST_NAME LAST_NAME ADDRESS Mary Simpson P.O. Box 32453 Dr. Joseph P. O'Brien 17434 Oak, Suite #201 This is much easier (and safer) to view and edit. But notice the wasted blank "white space." continued . . . Using DBF-ASC (continued) 12 Syntax: dbf-asc dbase.dbf ascii.fil <enter> "dbase.dbf" is the name of an existing dBase file. "ascii.fil" is the name of the ASCII file you want to create. If we can't find dbase.dbf, we'll tell you so and end. If ascii.fil exists, we'll ask if you want to Overwrite it or Quit. DBF-ASC will read the field structure of dBase.dbf, then let you edit, add or delete fields. Press F2 to save ascii.fil, or ESCAPE to quit. Requires: Free disk space equal to the size of dbase.dbf. NOTE: This should be enough to save ASCII ver- sions of dBase files. That's because ASCII files usually have less wasted "white space," and there- fore consume less disk space than their dBase cousins. Definition files are NOT required since we read the database structure from the dBase file. dBase Since DBF-ASC does NOT save dBase files, we needn't Limitations: follow it's strict rules regarding field names, types, etc. But, remember that you can save the field definitions to definition files. You can later read these (and an ASCII data file) to create dBase files. Here, following dBase rules is important. So: : : * You should NEVER change the names of existing dBase fields. If you do, when we try to save the information from those fields to your ASCII file, we won't find the field and your data won't be saved. * Further, if you ADD fields (to create blank, placeholders), and will later want to create a dBase file from your ASCII file, you must observe dBase's conventions for field Names, Types, Widths and Decimal Columns. Please see SECTION II, and our earlier dis- cussions for details on dBase restrictions. continued . . . Using DBF-ASC (continued) 13 Running dbf-asc dbase.dbf ascii.fil <enter> DBF-ASC: Replace "dbase.dbf" with the name of an existing dBase file, and "ascii.fil" with the name of the comma-delimited ASCII file you want to create. Be sure to specify a drive/directory if: - dbase.dbf is elsewhere. - Or, you want to create ascii.fil on a drive/ directory other than the one you're on. If we can't find "dbase.dbf" we'll print an error message and end. If "ascii.fil" already exists, we'll ask if you want to Overwrite it or Quit. continued . . . Using DBF-ASC (continued) 14 When DBF-ASC runs, it reads the field definitions of the dBase file you mentioned, then displays this screen: █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█ █ Field # Decimal ┬ █ █ # Field Name Type Width Places │ Esc = Cancel █ █───────────────────────────────────────┤ F2 = Save █ █ 1 First_Name C 15 0 │ █ █ 2 Last_Name C 15 0 │ ctrl-A = Add Field █ █ 3 Address C 20 0 │ ctrl-D = Delete " █ █ 4 City C 20 0 │ █ █ 5 State C 2 0 │ Tab/CR = Move Right█ █ 6 Zip_Code C 10 │Shft-Tab = Move Left █ █ ├─────────────────────█ █ ^ │# Fields = 6 █ █ │ │Rec. Len = 82 █ █─────────────┼─────────────────────────┴─────────────────────█ █ │ █ █▄▄▄▄▄▄▄▄▄▄▄▄▄│▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█ │ └───┐ In the main body ─┘ edit any field, or add or delete fields. Press: To: ───────── ───────────────────────────────────────────────── F2 Save your ASCII file with the fields you see. Esc Quit -- either to cancel the action, or to exit the program after you save your file. Up/Down Move up or down to highlight a field you want to PgUp/PgDn review or edit. Ctrl-Home/ Move to the top or bottom of the list. Ctrl-End Tab/Enter Move right on a line. Shift-Tab Move left on a line. Ctrl-A Add/Insert a field at the line that's highlighted. Ctrl-D Delete the field that's highlighted. Ctrl-Home Erase the contents of a field. Ctrl-End Delete from the cursor to the end of the field. Alt-U UnDo the last edit. For example, if, by mistake you pressed Ctrl-Home and erased the name of a field, press Alt-U to restore the original. NOTE: Alt-U will undo ONLY editing changes. It will NOT restore fields you delete with ctrl-D! continued . . . Using DBF-ASC (continued) 15 Editing or Adding Fields ──────────────────────── To create ASCII files, DBF-ASC needs to know only the NAME of each field you want saved. The field Widths, Types and # of Decimal places are irrelevant when saving data in ASCII. You may delete (ctrl-D) any field you don't want saved to your ASCII file. And you may ADD fields. Since these don't exist in the dBase file, we can't save any data. But this is con- venient to create blank placeholders you'll later add data to. NOTE: If you ADD fields and want to save a definition file you'll later use to create a dBase file from an ASCII file, you should strictly follow the dBase conventions when adding Type, Width and # of Decimal Places for fields you add. ALSO NOTE that if you add fields 2+ times, we'll duplicate the data. When You Press F2 ───────────────── When you ask to save your ASCII file, DBF-ASC asks 2-3 questions: * Registered versions ask if you want deleted records included. Shareware versions save everything. * All versions ask: Should I save the Deleted Record Flag? * All versions ask: Should I save a definition file? By convention, all dBase files begin each record with a 1-column field called the Deleted Record Flag. When programs delete records, they often delete nothing. They simply put an "*" in that 1st column, which tells the program this record was deleted. In registered versions you can tell DBF-ASC to save either all records, or just those that haven't been deleted. If you ask that all records be saved, we'll ask if you'd like to include the Deleted Record Flag. Answer Yes IF you'll ever use this ASCII file to create a dBase file AND you'll want to know if a record was deleted or not. We recommend that you ALWAYS say YES -- Save a Definition File. This file takes little space, is easily deleted if you find you really don't need it, and comes in handy in two ways. * First, ASC-DBF needs a definition file like this to create dBase files from ASCII files. * Second, definition files help you identify which fields are where. Since ASCII files have little if any white space, they're sometimes harder to apprehend visually than fixed- space files. Definition files help determine what's where. continued . . . Using DBF-ASC (continued) 16 Errors That Might Occur ─────────────────────── IMPORTANT: DBF-ASC will NOT tell you if it can't find a field name in the dBase file. That's because you might intentionally add fields to create blank placeholders. Obviously, if we can't find a field in a dBase file, we can't tell if it's an empty placeholder name, or a misspelled field name. So, if we can't find a field in the dBase file, we'll assume YOU added it; we'll just save a blank placeholder. Therefore, you should take care NOT to change names of EXISTING dBase fields. * If errors occur, we'll normally display an error number. Consult SECTION III to determine why the error occurred. Try to fix the error, then try saving again. Using ASC-DBF 17 ─────────────────────────────────────────────────────────────── Name: ASC-DBF.Exe. Purpose: * Create dBase files by reading data from comma-delimited ASCII files. * ALSO SEE the companion program DBF-ASC.Exe. Together, DBF-ASC and ASC-DBF let you quickly go back and forth between ASCII files (which are space-efficient, but hard to review and edit) and dBase files (which PDT lets you view and edit easily, but which are less space-efficient). NOTE: Database programs, word processors, spread- sheet programs, etc., often save data in their own, unique format. The comma-delimited ASCII format has evolved as an industry-standard way for programs to share data amongst themselves -- overcoming the limitations of their proprietary data formats. ASC-DBF is a v-e-r-y fast way to read ASCII files saved by one program, and create dBase files you'll use with different programs (like PDT). ┌───────────────────────────── TIP ──────────────────────────────┐ │ │▄ │ We often get comma-delimited ASCII files from clients. They │█ │ need their data edited or repaired. As we mentioned earlier, │█ │ these things are a nightmare to view and safely edit. │█ │ │█ │ So we run ASC-DBF. We quickly create a dBASE file that's │█ │ v-e-r-y easy to view and edit in PDT (and other programs). │█ │ Once we've edited the file, we use DBF-ASC to create an ASCII │█ │ version to return to our client. │█ │ │█ └────────────────────────────────────────────────────────────────┘█ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ ┌───────────────────────────── NOTE ─────────────────────────────┐ │ │▄ │ ASC-DBF differs from other programs in the Tool Kit in one, │█ │ very important way. Like CREATE, ASC-DBF gets dBase field │█ │ definitions from definition files you create. │█ │ │█ │ But unlike CREATE, ASC-DBF will NOT let you Add or Delete │█ │ fields. You CAN edit field names, types, widths, etc. But, │█ │ to Add or Delete fields, you must edit the definition file. │█ │ │█ │ Why? Because this is the safest way to read ASCII files, and │█ │ ensure we read each field and correctly save dBase files. │█ └────────────────────────────────────────────────────────────────┘█ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ continued . . . Using ASC-DBF (continued) 18 Syntax: asc-dbf definition.fil ascii.fil dbase.dbf <enter> "definition.fil" is the Definition File that either you or DBF-ASC created. "ascii.fil" is the name of your data file in ASCII format. "dbase.dbf" is the name of the dBase file you want to create. If we can't find definition.fil or ascii.fil, we'll tell you so and end. If dbase.dbf exists, we'll ask if you want to Overwrite it or Quit. ASC-DBF reads the field structure from the defini- tion file, then lets you edit, add or delete fields. Press F2 to save dbase.dbf, or ESCAPE to quit. Requires: ASC-DBF requires a definition file indicating: 1. The order fields will be coming in; 2. Which fields we should SKIP (field width is -1); and, 3) the dBase field definitions for fields we'll keep. ASC-DBF also requires free disk space equal to TWICE the size of ascii.fil. The reason for 2 times the size of ascii.fil is that we'll be creating a data file with more blank white space than is ascii.fil has. Until we start saving dbase.dbf, we can't know if there will be enough available disk space. So we recommend that you always ensure that free disk space is at least THREE TIMES the size of ascii.fil. dBase dBase places restrictions on field names, types Limitations: and widths. SECTION II has details. Briefly: Field NAMES: 10 characters maximum. They should begin with A-Z, and may contain A-Z, 0-9 and "_" (the underscore). Names WILL be capitalized, but you may enter them in upper or lower case. Field TYPE Field types include C, N, D, L and M. and WIDTH: The width of some field types is fixed: Symbol Type Width ══════ ═════════ ═══════ C Character 1 - 254 D Date 8 M Memo 10 L Logical 1 N Numeric 1 - 15 continued . . . Using ASC-DBF (continued) 19 Running asc-dbf definition.fil ascii.fil dbase.dbf <enter> ASC-DBF: Replace "definition.fil" with the name of the Definition File either you or DBF-ASC created. Replace "ascii.fil" with the name of your ASCII data file, and "dbase.dbf" with the name of the dBase file you want to create. Be sure to specify a drive/directory if: - Your definition or ASCII files are elsewhere. - Or, you want to create dbase.dbf on a drive/ directory other than the one you're on. If we can't find "definition.fil" or "ascii.fil" we'll print an error message and end. If "dbase.dbf" already exists, we'll ask if you want to Overwrite it or Quit. IMPORTANT SECTION II explains how to create Definition Files. NOTES: But, definition files used with ASC-DBF differ from others in two, very important ways: * First, they define each field in the ASCII file, NOT the dBase file you're creating. * For each field in the ASCII file, there must be one line defining that field. For fields in the ASCII file you DON'T want saved to the dBase file, enter -1 for # of columns. This enables us to read the field (which we MUST do), but skip it when saving dBase.dbf. In the example below, we're going to save fields 1 & 2, skip #3, then save #4. ............................. Line 1 ............................. Line 2 ............................. Line 3 ............................. Line 4 15 , C , First_Name Line 5 15 , C , Last_Name Line 6 -1 , C , CODE Line 7 25 , C , Company Line 8 continued . . . Using ASC-DBF (continued) 20 When ASC-DBF runs, it reads the field definitions from your definition file, then displays them in a screen like this: █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█ █ Field # Decimal ┬ █ █ # Field Name Type Width Places │ Esc = Cancel █ █───────────────────────────────────────┤ F2 = Save █ █ 1 First_Name C 15 0 │ █ █ 2 Last_Name C 15 0 │ █ █ 3 Address C 20 0 │ █ █ 4 City C 20 0 │ █ █ 5 State C 2 0 │ Tab/CR = Move Right█ █ 6 Zip_Code C 10 │Shft-Tab = Move Left █ █ ├─────────────────────█ █ ^ │# Fields = 6 █ █ │ │Rec. Len = 82 █ █─────────────┼─────────────────────────┴─────────────────────█ █ │ █ █▄▄▄▄▄▄▄▄▄▄▄▄▄│▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█ │ └───┐ In the main body ─┘ you may edit any field (but not add/delete). Press: To: ───────── ───────────────────────────────────────────────── F2 Save your dBase file with the structure you see. Esc Quit -- either to cancel the action, or to exit the program after you've saved your dBase file. Up/Down Move up or down to highlight a field you want to PgUp/PgDn review or edit. Ctrl-Home/ Move to the top or bottom of the list. Ctrl-End Tab/Enter Move right on a line. Shift-Tab Move left on a line. Ctrl-A/ NOTE these are NOT mentioned above! To add/delete Ctrl-D fields, do so in the Definition File, not here. Ctrl-Home Erase the contents of a field. Ctrl-End Delete from the cursor to the end of the field. Alt-U UnDo the last edit. For example, if, by mistake you pressed Ctrl-Home and erased the name of a field, press Alt-U to restore the original. NOTE: Alt-U will undo ONLY editing changes. It will NOT restore fields you delete with ctrl-D! continued . . . Using ASC-DBF (continued) 21 Editing or Adding Fields ──────────────────────── To emphasize, you may NOT add or delete fields in the edit window above. To do so, edit your Definition File instead. Since we'll be saving dBase files, you must observe the dBase conventions mentioned earlier. To help ensure that you do, as you move right or left from Name to Width to Type, etc., at the bottom of your screen we'll remind you what you can enter in each column. And if you enter illegal values, ASC-DBF will beep and point out the error. Although ASC-DBF won't allow blank field names, it WON'T check to see if names are valid until you press F2 to save your dBase file. At that time, if an error occurs, ASC-DBF will beep, tell you which error occurred, and tell you the number of the field where the error occurred. Press a key, fix the problem, then press F2 again. Errors That Might Occur ─────────────────────── There are two types of errors that might occur: 1. Those that occur when reading your ASCII file. 2. Those that occur when saving your dBase file. Of the two, the first are sometimes the hardest to track down and fix. That's because: ASCII files have variable-length records, fields are not conveniently laid out in columns, and there's little white space helping you spot each field. * The format of comma-delimited ASCII files is critical! - Each field should be surrounded by quotation marks. - Fields must be separated from each other by a comma. And there must be NO comma following the last field. - And, each record MUST have exactly the same number of fields. While it's technically not required that each field be surrounded by quotation marks, doing so ensures that commas inside a field aren't mistaken for the end of the field. For example, "Marion, OH 64323" has a comma separating City and State. If this field was NOT surrounded by quotes, that comma would be read as the end of this field. From that point on, EVERY field in EVERY record would be off by 1. continued . . . Errors (continued) 22 * As we mentioned above, each record MUST have the same number of fields as every other record. If, for example, one record had one field missing, from that point on, EVERY field in EVERY record will be off by 1 in your dBase file. * Similarly, if, when creating your definition file, you forget fields, or add too many, you'll get similar results: Beginning with the 1st or 2nd record, EVERY field in EVERY record in your dBase file will be off. As you can see, these errors are usually caused by errors in the ASCII file itself, or errors in the definition file that defines the data. Finding and fixing errors like these is often easier if you open the DBASE file in PDT, then scan records from the top to the bottom looking for where the error occurs. * If you see errors right away (fields not lined up in columns) the error is probably in the definition file: you defined too many or too few fields. If this happens, you'll often see data NOT lined up in columns. It might, for example, start going down the screen diagonally -- but in a consistent pattern from the top of the file to the bottom. * Pick a field that's easy to recognize (names, phone numbers, mail codes, etc.) then scan that field top-to-bottom. If everything looks OK for a while, then turns sour, chances are the definition file is fine, but the ASCII file is damaged -- perhaps one record is missing a field. If the problem seems isolated to just a few records, you might be able to fix the dBase file in PDT. But if many records are affected, note the last GOOD record, exit PDT and load the ASCII file into a file editor. Search for the last GOOD record, then examine it and the one beneath it for the error. Fix the problem, then run ASC-DBF again. continued . . . Using ASC-DBF (continued) 23 Errors that occur when saving dBase files are listed in SECTION III. They include: * DOS errors (you ran out of disk space; a disk was bad, etc.) * dBase errors (invalid or duplicate field names, etc.) * Internal errors (out of memory, etc.) When these types of errors occur, we'll normally tell you what happened, then let you try again. Consult SECTION III, try to fix the error, then press F2 again. If you're not sure what to do, call us. Please be at your PC (with it running), and be ready to repeat the steps you followed just before the error occurred. If it's not pos- sible to be at your PC, at least tell us very specifically what you were doing, what happened, and what error messages you got. 24 ─────────────────────────────────────────────────────────────── SECTION III: Creating Definition Files ─────────────────────────────────────────────────────────────── "Definition Files" are used by several of the programs in PDT's Tool Kit. You can create them with any editor or word processor. They must be saved in ASCII (or DOS text) format. That means: * They must have no formatting codes like the ones word pro- cessors use to symbolize font changes, line spacing, etc. * Each line must end with a carriage return/line feed. Both of these conditions are usually met if you use your word processors ASCII or DOS text option to save the files. ┌───────────────────────────── NOTE ─────────────────────────────┐ │ │▄ │ If you've used PDT, you're probably familiar with PDT's │█ │ "structure files." Definition files resemble structure │█ │ files -- but there are some v-e-r-y important differences: │█ │ │█ │ Definition Files Structure Files │█ │ ──────────────── ─────────────── │█ │ * Lines 1-4 Ignored (instructions) Used │█ │ │█ │ * 1st entry of │█ │ Field Def: Field WIDTH (or -1) Field START │█ └────────────────────────────────────────────────────────────────┘█ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Definition Files have the following basic format: Instructions to you (required) " " " " " " " " " " " " Width , Type , Name Lines 1-4 contain instructions to you. They may contain ANYTHING (they can even be blank). But they must be there. Beginning on line #5, add 1 line for each field. * Each line must have 3 sections separated by 2 (and ONLY 2 commas): Field Width, Field Type, Field Name. this is VALID: 22 , C , First_Name this is INVALID: 1,200 , C , Memo_Data In the 2nd, invalid example, there are 3 commas. The error is in "1,200." It should read: 1200, C, Memo_Data. * "22, C, First_Name" describes a "C" (Character) field 22 characters wide named "First_Name." Field Types 25 ─────────── Here are the symbols you'd enter to indicate field TYPES. ══════ dBase Field Types ═════ ═══ Non-dBase Field Types ════ Use This For This Field Use This For This Field Symbol Type of Field Width Symbol Type of Field Width ──────── ───────────── ───── ──────── ───────────── ───── C Character 1-254 c Character ? N Numeric 1-15 t Tiny Integer 1 L Logical 1 i Integer 2 M Memo 10 l Long Integer 4 D Date 8 s Single MS 4 j Single IEEE 4 d Double MS 8 k Double IEEE 8 $ Currency 8 ┌─────────────────────── TIPS & NOTES ────────────────────────┐ │ │▄ │ Note that symbols for dBase files are UPPER case, while │█ │ symbols for non-Dbase field types are all in lower case. │█ │ │█ │ In the non-dBase list, note the s/j and d/k pairs -- indi- │█ │ cating Microsoft (MS) versus IEEE formats, respectively. │█ └─────────────────────────────────────────────────────────────┘█ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Field Widths ──────────── Depending on the field TYPE, the width of the field may be fixed or variable. The column "Field Width" indicates how many characters/columns each field was allocated. Notice that Character fields (and dBase Numeric fields) are "?" wide -- they vary in width. But other fields have fixed widths. An easy way to determine the width of fields is to load a file into PDT, put your cursor on the 1st character of a field, press ctrl-B (begin marking a block), move the cursor right to the end of the field, then note the number PDT shows you in the lower left corner of the file window: "BLK: ###." ┌─────────────────────── REMEMBER: : : ───────────────────────┐ │ │▄ │ When creating definition files to read comma-delimited │█ │ ASCII files, use a field width of "-1" to indicate fields │█ │ we should skip. NEVER just ignore the field! │█ │ │█ └─────────────────────────────────────────────────────────────┘█ ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Field Names 26 ─────────── Compared with dBase, PDT and the programs in the PDT Tool Kit are more flexible and tolerant regarding field names. * We won't let you enter blank field names. * But if you enter a name with spaces (eg., First Name), we'll just close it up for you when we save it to a dBase file -- since dBase won't accept blanks. Please try to closely follow dBase's field name conventions: * Field names may be 1-10 characters in length. * They MUST start with a letter (A-Z). * You may use A-Z, 0-9 and the underscore -- ONLY. Note you may not included spaces, punctuation, or high or low ASCII characters. * They're ALWAYS stored in upper case. In definition files you can use any combination of upper and lower case. But you might want to use upper case to see how recognizable they'll be when actually saved to dBase files. 27 ─────────────────────────────────────────────────────────────── SECTION IV: Summary and Explanation of Error Message ─────────────────────────────────────────────────────────────── We've mentioned before that the programs in the Tool Kit WILL: * Try to prevent you from entering blank field names or illegal values for field Type or Number of Decimal Places. * Alert you if they find illegal field names (such as ones with characters other than A-Z, 0-9 and the underscore. (Field names MUST start with a letter.) * Alert you if they find duplicate field names. In the latter two cases, we'll point out the error and the line on which it occurred. You can then fix the error and save your file again. For other errors, depending on what you're doing, we may be able to recover and let you fix the error, or we may exit to DOS. There are 3 general categories of errors: DOS, dBase File Errors, and Memory or Expression errors. DOS Errors # Description ────────── ─── ───────────────────────────────────────────── 1 Invalid function number (unlikely) 2 File not found 3 Path not found (invalid drive or directory) 4 Too many files open (increase FILES = ) 5 Access denied (Locked file; write protected disk) 15 Invalid drive specified 18 No more files of this type 19 Disk write protected 20 Unknown unit/device 21 Drive not ready 23 Data error (could mean corrupted data) 25 Seek error 26 Unknown media type 27 Sector not found (could mean damaged disk) 29 Write fault ( " " " " ) 30 Read fault ( " " " " ) 31 General failure ( " " " " ) 80 File already exists DBASE Errors # Description 28 ──────────── ─── ───────────────────────────────────────────── 100 Internal error 101 " " 102 Error in file name 103 Erroneous file type 104 Invalid file handle (internal error) 105 File not in state to perform requested action 106 Field Name error 107 Nor fields have been defined 108 Too many fields were defined 109 Field name already defined (duplicate name) 110 Error in field length 111 Too many decimal places 112 Total record length too large for file type 113 Wrong record number or sector address 114 Wrong record string length 115 File is not a valid .DBF file 116 Field number is not valid for file type 117 Wrong value requested for file mode 118 Internal error -- bad buffer 119 Field not found in dBase file 120 File is not a valid .NDX file 121 Key expression is too long 122 Key not found in index 123 End of index encountered (key not found) 124 Duplicate keys not allowed 125 Key or Key Length is too long or too short Memory/ Expression Errors # Description ───────────── ─── ───────────────────────────────────────────── 126 Insufficient (out of) memory 127- Memory errors 130 143- Memory errors 147 131- Errors in expressions 140 141 Divide overflow 142 Illegal function or empty string 148 Invalid date argument 149 Invalid date format 29 ─────────────────────────────────────────────────────────────── SECTION V: Using FIX-DBF Structure Files. Exploring or Repairing dBase files. ─────────────────────────────────────────────────────────────── Fix_DBF.Hdr and Fix_DBF.Fld are PDT structure files that can prove invaluable if you ever need to repair or simply examine dBase files. You can use these to explore ANY dbase file. Even if you never use these files, this section can give you valuable insights into how dBase files are set up. This section is sent to PDT's registered users. 30 ══════════════════════════════════════════════════════════════ APPENDIX I: Other Programs by Pro~Formance Here's a summary of many of our other programs. ══════════════════════════════════════════════════════════════ ══════════════════════════════════════════════════════════════ Professional Scribe (Pro~Scribe) PS Express (PSE) ══════════════════════════════════════════════════════════════ Pro~Scribe and PSE help you improve anything you write (or help you improve the writing of others -- your staff, students, etc.) Pro~Scribe is used around the world in companies like IBM, Hewlett Packard, AT&T, Lockheed, Citicorp and Bank of America to help improve memos, letters, manuals, documentation, contracts, promotional material, etc. Here's how Pro~Scribe and PSE help: * They examine your writing for many types of writing mistakes. * You can look at overall results for an entire letter, report, etc. Or, if you like, they'll look at your writing line-by-line. * They show suspect problems, and offer suggestions. * Results are shown numerically, and with colorful graphs. * They come with two manuals (plus a Quick Reference Guide) - One covers basics: To install/run PS, and basic guidelines. - "Effective, High-Impact Writing" has more writing tips. * They're colorful, fast, fun, and a terrific value: $39 for both! How are Pro~Scribe and PSE different? First, PS Express is a RAM-resident program. That means it's always ready to help when you need help most--while you're actually writing. Run PSE, then run your word processor and start writing. Need help? Just press a key. * When PSE pops up, just mark the text you want PSE to examine. A window pops up instantly with feedback on your writing. * PSE is like having an English teacher looking over your shoulder, gently coaching you as you write. Pro~Scribe gives you everything PSE does, and much, much more. It reads files saved by your word processor, or you can type text directly into PS. Like PSE, Pro~Scribe shows how complex your writing, words and sentences are. It also offers you: * Feedback on "Word Wasters" (5 categories of writing errors). * Three RGL (Running Grade Level) options (line-by-line feedback). * An option to flag complex words and Word Wasters in each line. * A Personal Interest score showing if you write as you speak. * Options to: Customize the program, send results to your printer. 31 ══════════════════════════════════════════════════════════════ Multi-Print The ultimate text printing utility! ══════════════════════════════════════════════════════════════ Multi-Print (MP) prints ASCII text files (like this manual) on HP LaserJets -OR- Epson -OR- Toshiba printers (or compatibles). * Print 1, 2 or 4 PAGES of text on each SHEET of paper. Print in portrait mode on BOTH sides of the paper on ANY printer, Or print sideways on LaserJets, Epson or Toshiba printers. - Choose "Booklet" mode to print books. Print the "front" side, then the "back." Then just fold it into a booklet and staple! - Choose "Left-to-Right" to print pages side-by-side, first on the left side of the page, then on the right. - Choose "1 Column" per sheet to print up to 250 characters per line (this is great for printing spreadsheets). - And with the last 2 options, you can choose to print 2-sided or 1-sided. Then use them as-is, or slip them into a 3-ring binder. (Booklets are always printed 2-sided). * Four fonts are included. - Our 9-point Times Roman font is a better-looking substi- tute for the LaserJet's "Line Printer" font (though you can use the Line Printer font if you wish). With our 6- point Roman font, print up to 250 characters/line and 80 lines/page (eg., spreadsheets). - Other fonts let MP print "sideways" on Epson and Toshiba printers. * The four fonts contain almost all ASCII characters. Print: - Lines, boxes, shading, Big! Fonts (tm). - French, German, Spanish and other language characters. - "Control codes" (with ASCII values below 32) which are useful when you want to add arrows, "bullets," "check boxes" and other symbols to your text. - NOTE: Original LaserJets and LaserJet + can't print the last 2. * MP offers many printing options: - Print TITLES: page numbers, the date, and the name of the file you're printing (or a "custom title") - in any com- bination. Print titles at the TOP or BOTTOM of each page in several "styles." - Print "both" sides, or just the "front" or "back" side. - Control Top, Left and Right Margins. "Wrap" long lines of text (LaserJets only). Print to LPT1, 2 or 3 or "to a file." Etc. * MP is menu-driven; choose options using a mouse or the keyboard. 32 ══════════════════════════════════════════════════════════════ inform-Z (also see Mail Call below) Professional Forms Design ══════════════════════════════════════════════════════════════ inform-Z is a complete form system. Built-in features include: easy form design, math, "auto-edit," high quality printing, etc. Design, edit and print forms with inform-Z. * Draw lines or boxes, or add shading, in several styles. * Enter text, auto-centered inside boxes if you like. * Automatically date, sequence number and time-stamp forms. * Add "formulas" for spreadsheet convenience, speed & accuracy. * Quick, easy block options: Copy, Move, Erase, Shading. * Vary fonts, type styles, line spacing. * inform-Z is very easy to use. And it's "lesson forms" cut the learning time dramatically. Then use inform-Z or Mail Call to fill out forms. * "Auto-Edit" fields lets you quickly skip through a form, editing just fields you "marked." On order forms, for example: Quantity, Description, Price per Unit. Math options will do the math for you! * Let Mail Call fill in other information for you -- pulling names, addresses, etc. from your database, putting them where you want them. Produce high-quality, professional looking forms in minutes with Epson printers or HP LaserJets (+/500/Series II or later). And you DON'T need expensive font cartridges or soft fonts for lines, boxes, shading, etc. We use built-in features for these. "But, I don't have a LaserJet or an Epson" you say. Not to worry. inform-Z has two other printer options so it works with any printer. Together, inform-Z and Mail Call can help you manage almost every piece of paper in your office. Forms: Invoices, Purchase Orders, Personnel Forms, Work Orders, Work Schedules, Travel or Expense Reports, Accounting Forms, Application Blanks, Org. Charts As Well As: Letters, Memos, Envelopes, Mailing Labels, Personalized Documents (ie., form letters), Reports, Client or Employee lists, etc. 33 ══════════════════════════════════════════════════════════════ Mail Call and MC Express (MCE) Our mailing assistant ══════════════════════════════════════════════════════════════ Mail Call (MC) is a full featured mailing assistant. Add names to a database, then Browse, Search, Print, Sort, etc. * Print envelopes in several sizes. * Print mailing labels (several sizes plus a "roll-your-own- size" option) 1 to 99 copies of each label, 1 to 3 columns across. * Print personalized documents (or form letters). * Print forms -- with "auto-edit," date, sequence number and math features! * Print reports, phone books, appointment schedules, etc. Mail Call offers UNlimited capacity -- use as many database files as you want. And its "Mail Merge" option lets you Import or Export names to files used by word processors or other database programs. MC Express, a "RAM-resident" program, that lets you: 1) print envelopes while INSIDE your word processor; and, 2) lets you "write out" names & addresses to a file you can later "import" into MC (no re- typing). MCE, optional, works with ALL versions of the HP LaserJet. 34 ══════════════════════════════════════════════════════════════ P~F Presents (PFP) A DESKTOP PRESENTATION System ══════════════════════════════════════════════════════════════ P~F Presents comes with several programs to help you create, manage and display presentations. The two main programs are P-Screen and PFP. With P-Screen you: (See below for more on P-Screen) ────────────────── * Design screens (or "slides"). * Save screens in libraries (or print them, or save them to ASCII files, or executable ".COM" files.) * NOTE: We offer TWO "screen-capture" programs to help you capture screens from existing applications. One captures text screens. The other captures ANY type of screen! With PFP you: ───────────── * Create presentation agendas ("slide shows") which can include: - Menus which "branch" to various parts of your presentation, depending on the option your viewer selects. For example: -- Which product do you want information on? -- Which topic (in a tutorial) do you want to review? - Timed slides (PFP pauses, then automatically shows the next) - Special effects: animation, sound, loops, exploding windows * Display your presentations, or let others do it by them- selves. A "use monochrome" option lets you display presen- tations on virtually any monitor. The Possibilities are Endless: ────────────────────────────── * Sales presentations * Management/Staff briefings * Training programs * Tutorials or Demos * Meetings * Highlight product information * Investment opportunities * Advertising on disk (SoftAds) * Customer information * Tourist guides * Restaurant guides * Directories (Names, phone #s) And on and on and . . . 35 ══════════════════════════════════════════════════════════════ P-Screen & P-Screen Professional QuickBASIC screen support ══════════════════════════════════════════════════════════════ P-Screen is a screen: "design," "library/database" and "display" system all in one. Use it to design screens for programs you write, or for program demos, prototyping, word processing, batch files, etc. * Draw/Join lines or boxes in several styles. * Shade or Paint entire screens or selected areas. * Enter text, auto-centered inside lines or boxes if you like. * Quick, easy block options: Copy, Move, Erase, Shade, Paint, UnDo. Save/Load/Libraries * Save screens to or Load screens from ASCII files or Libraries. You can also save executable "Com" screens -- colors and all! - We include a program to "grab" screens from other applications. * Libraries give you 1-file convenience of storing up to 100 screens -- in color, complete with names and descriptions. Using screen libraries in your programs, demos, etc. * We supply routines to display your screens from QuickBASIC programs (QB 3-4.x or PDS 7.x). * It's easy to write programs to access screen libraries. - You can load and display 1 screen at a time. - Or load 2 or more screens into arrays, then pop them up instantly. P-Screen Professional even writes your QB programs for you!! And it comes with several other subprograms you can use in any program. Call for **significant** details. 36 ══════════════════════════════════════════════════════════════ The Survey Catalyst (A commercial program, not Shareware) ══════════════════════════════════════════════════════════════ The Survey Catalyst (TSC) is for anyone who works with attitude or opinion surveys. It helps you create surveys in minutes or hours -- not days! * TSC includes a database of thousands of survey items--like items used in most Fortune 1000 companies' employee surveys. - You can review items, edit them or add new ones. - OR, when you see an item you want to add to a survey, just press a key and add it--fast and simple. * TSC also comes with dozens of response scales. When you print surveys, TSC prints the right response scale--automatically. * And speaking of printing, TSC's many options let you create "camera-ready" copy--as you want it, fast! - Group items by Category, by Response Scale, or Randomize them. - Print response scales Above or Beside items (or not at all). - Print key punch instructions (optional) - Print a title--at the top or bottom of each page. - Or, print your survey "to a file"--to dress it up later. ══════════════════════════════════════════════════════════════ Pro~Stamp Stamp Collection Manager ══════════════════════════════════════════════════════════════ Pro~Stamp is our full-featured stamp collection manager. * It's very easy to use: pull-down menus, extensive on-line help; Calculations done for you, select "Type" & "Condition" from menus, and more. * Your worksheets are set up like most popular collectors' manuals (eg., Scott). * Track small to huge stamp collections, with ease and convenience. * Multiple file options add flexibility (subsets of collections) * Automatic calculations (Values of each stamp, Increase in value) give you spreadsheet convenience. * Sort: On any of several fields. * Print: Entire worksheets or a range you specify. * It's customizable: Edit menu items or printer codes your way. 37 ══════════════════════════════════════════════════════════════ Ram-Man RAM-resident file browser ══════════════════════════════════════════════════════════════ Ram-Man is a RAM-resident (TSR) program to turn ANY text file into a pop-up quick-reference guide (or manual). For example, keep THIS MANUAL at your fingertips while learning inform-Z! * Pop up your text file while you're working in virtually any text-based (not graphics) program (including inform-Z). * BROWSE through it. * SEARCH, looking for a topic or phrase you're interested in. * LOOK UP words, which we'll read directly from your screen! We supply the RAM-resident "engine," you supply the text. Ram- Man preserves DOS memory by keeping ONLY its engine in memory. It displays your text from disk (hard or RAM disk recommended). You can change which file you're viewing without unloading Ram-Man. That means you load Ram-Man once, then change ref- erence guides as your needs or the programs you use change. Now, regardless of which text-based program you're using (or even at the DOS prompt), you can have on-line, pop-up help available -- at any time, at the press of a key. Examples: * The complete, on-disk manual for a program you're using. * A series of help screens or "Quick Reference Guides" (eg., tips on using DOS, tips on using a program). - You can display standard DOS text files, like those you create using an editor or word processor. - Or you can display special "screens" you create with programs like our P-Screen Screen Designer. * Appointment Calendars, To Do Lists. . . . etc. Other features: (<R> = REGISTERED versions.) * BROWSE through files -- line by line or page by page. And you can jump to the top or bottom of small -or- huge text files in 1/2 second or less. * SEARCH for topics relevant to your needs. * <R> "LOOK UP" reads a word directly off your screen THEN searches for it! BE SURE to read the section on Look Up for uses (eg., Quick reference, spelling, thesaurus, quotations). * UNLOAD Ram-Man and reclaim the memory it uses. * <R> RUN-TIME OPTIONS let you choose: - The "hotkey" you want to use to call Ram-Man up. - The size of the screen you want to use -- to let you switch between 25, 43 or 50 row screens at will. - The colors we use to display text. These options help ensure that Ram-Man's hotkey, colors and screen modes never conflict with the programs you use. 38 ══════════════════════════════════════════════════════════════ SPARKLE & MENU MAGIC Add some sparkle to your batch files. ══════════════════════════════════════════════════════════════ Sparkle is an AMAZING utility to enhance batch files, use from DOS, or use through other programs (via "shell"). And Sparkle now includes Menu Magic which lets you quickly create scrolling bar menus (see Menus below) and writes your batch files for you! One small (9k) program offers these many features: * MENUS Sparkle offers 3 menu options. Turn ANY screen into a menu. Or turn ANY text screen into a Vertical or Horizontal "scrolling bar" menu. * SOUND Over 35 sound effects, ranging from simple to the William Tell Overture! * WINDOWS Create windows (boxes) on screen in over 250 styles, with/without shadows, and in any color. * QuikPRINT Display text anywhere on the screen in any color. * ASK Ask the user to press a key -- to get a menu choice or to simply pause. - You can display any message you like in any color. - You can specify which keys are "valid." For example, suppose your menu had 3 choices and you ask someone to press 1, 2 or 3 to choose one of them. Just tell Sparkle that "123" are your "valid keys." Sparkle will wait until one of these keys (or Escape) is pressed -- then tell you which one was pressed. * PAUSE You can pause for brief moments (1/3 second) or for several minutes. And Sparkle even gives you the option to let your users "press a key" to interrupt a pause and move on. * MONITOR Determine what type of monitor is active. 39 ══════════════════════════════════════════════════════════════ VIDLIB A commercial-quality Video Tape Librarian ══════════════════════════════════════════════════════════════ VIDLIB has every feature that every other video tape program offers. And the author guarantees to add any feature another program has that VIDLIB doesn't. ANY feature ... GUARANTEED! VIDLIB stores 27 different pieces of information about each tape in your collection. - Tape number, recording's title, Category (adventure, romance, sci-fi, etc.), Rating (G, PG, R, etc.), origin (purchased, television, home recording, HBO, etc), stars appearing, director, studio, color or B&W, cost, date re- corded, recording speed, recording length, footage start and end, what language is spoken, subtitles?, cabinet and/or shelf where tape is stored, date the tape was loaned, who borrowed it. - No field is required! Use or ignore any information field you like. Use what you want; ignore what you don't. - Use 2 word processor-like windows to describe each record- ing on a tape and describe its honors, awards or nominations. - Depending on YOUR tastes, use the unique 5 star rating system to Rate each individual recording. - Many fields can be redefined by the user. VIDLIB handles an unlimited number of tapes with an unlimited number of recordings per tape. VIDLIB offers easy-to-use, yet surprisingly powerful printout support. - Print 3 different Avery labels available from your local office supply store: labels for the tape spine, tape face and the tape box. - Print 2 Rolodex and 3 index card formats and sizes. VIDLIB supports pin-feed Avery formats, too. - Three report formats including a beautiful catalog sheet and a special report for your insurance company! - Supports dot-matrix, laser or letter quality printers. VIDLIB is exceptionally fast on any computer, even XT's and PC's. It works handsomely on color or monochrome (black/white) monitors. And VIDLIB uses the popular dBase (DBF) file structure. So you can access, read and edit VIDLIB databases using dBase III, dBase III+, dBase IV, Clipper -- or our own PDT program. 40 ══════════════════════════════════════════════════════════════ APPENDIX II: Registering and Ordering ══════════════════════════════════════════════════════════════ Because we offer so many programs, our order form has 2 pages. * This page lists our programs and the per-copy cost of each. The section immediately above describes each or our programs. * The next page is the actual order form. On it, fill in the name of each program you're ordering. PLEASE BE CAREFUL here and use the names listed below. If we're not sure which program you are ordering, we may have to return you're order! If ordering by Visa or MasterCard, fill in the section for credit card orders. BE SURE TO SIGN it. Program Name Per Copy ────────────────────────────────────────────────────────────── Multi-Print Recommended! ($25 w/ purchase > $100) $39 PDT The Pro~Formance Data Tool $99 PDT Tool Kit The COMPLETE PDT Tool Kit (Pgms, Files +) $35 Set #1 Tool Kit Set 1: Create, DBF-DBF $19 Set #2 Tool Kit Set 2: DBF-ASC, ASC-DBF $19 inform-Z Professional Forms Design $49 Mail Call With MC Express $49 " " Without MC Express $45 Pro~Scribe & PS Express $39 P~F Presents Professional $79 " " Plus (with intro. copyright) $49 P-Screen Professional $49 " Plus $29 Pro~Stamp Stamp Collection Manager $29 Ram-Man RAM-resident Text File Browser $19 Sparkle AND Menu Magic $29 VidLib Video Tape Librarian and Database $39 The Survey Catalyst $595 " " " Demo Disk (refunded with purchase) $5 ───────────────────────────────────────────────────────────────── PACKAGE DISCOUNTS Call about quantity discounts & site licenses. ───────────────────────────────────────────────────────────────── inform-Z AND Mail Call $79 P-Screen Pro AND P~F Presents $109 (Professional versions of BOTH.) 41 ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ To Order ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ For FASTEST delivery of your programs, CALL with your Visa/MC card number. F ____________________________________________ M Rob W. Smetana Pro~Formance R ____________________________________________ A T 132 Alpine Terrace San Francisco, CA 94117 O ____________________________________________ I O (415) 863-0530 M ____________________________________________ L Make checks payable to Rob W. Smetana Phone ( ) ______-________ Date ___/___/___ ┌──────────────────────────────────────────────────────────────────────────┐ │ For Visa or MasterCard Orders │ ├──────────────────────────────────────────────────────────────────────────┤ │ │ │Credit Card Number: __________________________________ Expires: ___|___│ │ │ │Signature (Required for credit card orders): _____________________________│ │ │ │ Be sure your name at the top matches how it appears on your credit card. │ └──────────────────────────────────────────────────────────────────────────┘ ────────────────────────────────────────────────────────────── TK-Set2 1.4 ─ Program/Package Name (see last page) # of Copies Price/Copy Total ──────────────────────────────────────────────────────────────────────────── ________________________________________ ________ x ______ = $_______ ________________________________________ ________ x ______ = $_______ ________________________________________ ________ x ______ = $_______ ________________________________________ ________ x ______ = $_______ ________________________________________ ________ x ______ = $_______ ________________________________________ ________ x ______ = $_______ ──────────────────────────────────────────────────────────────────────────── Shipping & Handling::: Total Number @ $4/copy (US/Canada) of Programs (and Copies) ----->> _____ @ $8/copy (Elsewhere) $ _______ ─────────────────────────────┬────────────────────────────────────────────── │ Subtotal $ ________ INTERNATIONAL ORDERS: : : │ │ California residents, add 8.5% tax $ _______ * US funds only please. └─────────────────────────┬──────────────────── * Money order, check drawn a │ US bank, or VISA/MasterCard │ TOTAL $ ________ ───────────────────────────────────────────────────────┴────────────────────